Lte network extension (lne) system, methods, and apparatus

ABSTRACT

An LTE network extension (LNE) system includes an LTE access gateway (LAG) and a provisioned database. A plurality of LTE access radios in the LNE system broadcast the same shared PLMN ID (sPLMN ID). The sPLMN ID corresponds to a plurality of service provider core networks, each with a different PLMN. The provisioned database includes information identifying which networks are allowed to use the LNE system and includes service provider network address information. An LTE access radio, transmitting the sPLMN ID detects an attach request from a UE, and forwards the attach request to the LAG, which decides if access is to be allowed, based on a service provider home network PLMN included in an IMSI in the attach request and information in the provisioned database. If access is allowed, the LAG serves as a proxy between the LTE access radio and the UE&#39;s service provider home network.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/922,933 filed Jul. 7, 2020 which published as U.S. patentpublication US 2020-0336978 A1 on Oct. 22, 2020, which is a continuationof U.S. patent application Ser. No. 15/992,165 filed May 29, 2018 andwhich published as U.S. Patent Publication No. US-2019-0373535-A1 onDec. 5, 2019 and which issued as U.S. Pat. No. 10,708,855 on Jul. 7,2020 with each of the preceding patent applications and publicationsbeing hereby expressly incorporated by reference in their entirety.

FIELD

The present application relates to wireless communications methods andapparatus, and more particularly, to methods and apparatus for extendingcoverage in LTE communications systems.

BACKGROUND

Extending wireless coverage into new areas typically requires buildingnew sites that typically requires right of way (zoning) and capitalexpenditure which makes it costly and time consuming. Typically, if theservice providers does not have spectrum to operate in the area then theservice provider cannot build a wireless network in that area at all.

For a small service provider it may not be able to build new serviceareas fast enough to extend the reach and will have to sign expensiveroaming agreements with the willing service providers. If the cost ispassed on to the subscribers it may impede the subscriber growth.

An FCC initiative to open up 150 MHz of shared spectrum (3550 to 3700MHz) will encourage new entrants to the markets. It is expected that alarge number of private LTE networks will emerge using shared CBRSspectrum. Existing solutions may discourage new entrants if there is ano easy way to extend their service reach.

Some of the existing solutions to provide wireless services beyond homeservice areas are: roaming partnership, neutral host solution andnetwork partnership using MOCN (Multi Operator Core Network).

The roaming partnership solution will now be described. Roaming allowssubscribers to get services from a partner network. Roaming partnershiprequires financial and technical agreements that at times may not befinancially favorable for a small service provider. A large serviceprovider may not see any value in signing these agreements with a smallservice provider with only a few thousand subscribers. This might resultin discouraging small operators from building their own networks and dueto lack of roaming, and the small service provider may have troublesigning up more subscribers.

The neural host solution will now be described. Neutral host solutionscombines signals from multiple service providers and uses passivesolutions e.g. DAS (distributed antenna system) to distribute thecombined signal in the target area e.g. shopping mall, airport, sportsstadium etc. Participating in the neutral host system requires anyservice provider to build wireless network at target location to feedinto neutral host solution provided they have spectrum holdings to use.

The MOCN (Multi Operator Core Network) solution will now be described.LTE technology allows up to 6 service providers to share the radionetwork. Setting up of MOCN network requires a lot of co-ordinationamong service providers and is a very complicated set up since radioresources are shared across service providers. This architecture to savecost of setting up wireless network didn't get much traction in USA. Itis highly unlikely that a large operator will broadcast small operatorinformation on their radio network. MOCN architecture is also limited toa total of 6 service providers. Since shared CBRS spectrum is expectedto encourage a lot of private network builds, the MOCN architecturelimitation to support up to 6 service providers may become a bottleneckin wireless network sharing.

Based on the above discussion, there is a need for new methods andapparatus to extend wireless services in LTE communications systems.

SUMMARY

In various embodiments an LTE access radio, e.g., a small LTE basestation, operates as a shared host for one more service provider corenetworks. The number of service provider core networks can range fromone to a large number, e.g., 6, 7 or even more. In at least someembodiments the LTE access radio broadcasts a shared PLMN identifier(sPLMN ID) which identifies the access radio as a shared host and doesnot identify a specific service provider core network. UEs areprovisioned with the PLMN ID of their home network service providers andwhat are known as shared PLMN IDs (sPLMN IDs) because they are IDs whichthe UE can also use to access services via their home service provider.In various embodiments a shared PLMN ID, which can be used to access thehome service provider network, e.g., via an LTE network extension systemincluding an LTE access gateway, is stored in UEs allowing them toconnect to the home network via an access radio transmitting the sharedPLMN ID.

By designating a PLMN ID as a shared PLMN ID (sPLMN ID), a single PLMNidentifier can be broadcast by multiple different access radios with theservice provider core networks supported by the different access radiosusing the same PLMN identifier potentially, and in some cases actually,being different. The different access radios transmitting the sameshared PLMN identifier may, and sometimes do, support different numbersof service provider core networks. In this way the number of serviceprovider core networks a shared host can support is not limited by thenumber of PLMN identifiers it can transmit which in many cases islimited to 6 PLMN IDs.

In various embodiments the LTE access radio, transmitting the sharedPLMN ID, is coupled to the various service provider core networks whichit supports via an LTE access gateway (LAG). In accordance with variousfeatures, the LTE access gateway is coupled to or includes an LTE accessdatabase (LAD), which includes information on which service providercore networks are supported by individual shared host access radioswhich are coupled to the LTE access gateway.

In at least some embodiments the LTE access gateway becomes an accesspolicy enforcement point which is an addition to other access controlcomponents and functions which may be, and often are, located in theaccess radio and/or service provider core network system.

In various embodiments a UE seeking to obtain service from a serviceprovider core network with which the user of the UE has a serviceagreement, and thus the UE has a right to obtain service, may receivethe shared PLMN ID from a shared host access radio. After receiving theshared PLMN ID, a UE including the shared PLMN ID in its list of PLMNIDs as an sPLMN may, and sometimes does, seek to obtain services fromits home service provider core network via an access radio transmittingthe shared PLMN ID. The UE seeks to obtain services by sending an attachrequest to the LTE access radio transmitting the shared PLMN ID. In theattach message the UE includes its own mobile identity information,e.g., IMSI which includes as part of the IMSI an identifier of the UE'shome service provider core network which is to provide the UE itsservice.

An exemplary method of operating an LTE communications system inaccordance with some embodiments, includes: storing in a storage deviceservice provider core network access information for a plurality ofdifferent service provider core networks associated with a first sharedPLMN ID (sPLMN ID), said service provider core network accessinformation including a PLMN ID of each individual service provider corenetwork and corresponding address information for the individual serviceprovider core network for which a PLMNID is stored; operating an LTEaccess radio to transmit said first shared PLMN ID; and operating theLTE access radio to receive a first attach request from a first userequipment (UE) device.

While various features and methods have been described, all embodimentsneed not include all features or steps mentioned in the summary.Numerous additional features and embodiments are discussed in thedetailed description which follows.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a drawing of an exemplary communications system, e.g., an LTEcommunications system including an LTE network extension (LNE) system,in accordance with an exemplary embodiment.

FIG. 2A is a first part of an exemplary signaling diagram includingexemplary LTE Network Extension Call Flow in accordance with anexemplary embodiment.

FIG. 2B is a second part of an exemplary signaling diagram includingexemplary LTE Network Extension Call Flow in accordance with anexemplary embodiment.

FIG. 2C is a third part of an exemplary signaling diagram includingexemplary LTE Network Extension Call Flow in accordance with anexemplary embodiment.

FIG. 2 comprises the combination of FIG. 2A, FIG. 2B and FIG. 2C.

FIG. 3A is a first part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3B is a send part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3C is a third part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3D is a fourth part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3E is a fifth part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3F is a sixth part of a drawing of an exemplary Attach Requestmessage, which is used by a LAG to identify target PLMN (310-014), inaccordance with an exemplary embodiment.

FIG. 3, comprises the combination of FIG. 3A, FIG. 3B, FIG. 3C, FIG. 3D,FIG. 3E and FIG. 3F.

FIG. 4A is first part of a flowchart of an exemplary method of operatingan LTE communications system, e.g., an LTE communications systemincluding an LTE network extension (LNE) system, in accordance with anexemplary embodiment.

FIG. 4B is second part of a flowchart of an exemplary method ofoperating an LTE communications system, e.g., an LTE communicationssystem including an LTE network extension (LNE) system, in accordancewith an exemplary embodiment.

FIG. 4C is third part of a flowchart of an exemplary method of operatingan LTE communications system, e.g., an LTE communications systemincluding an LTE network extension (LNE) system, in accordance with anexemplary embodiment.

FIG. 4 comprises the combination of FIG. 4A, FIG. 4B and FIG. 4C.

FIG. 5 is a drawing of an exemplary LTE access radio (LAR) in accordancewith an exemplary embodiment.

FIG. 6 is a drawing of an exemplary assembly of components, which may beincluded in a LTE access radio (LAR) in accordance with an exemplaryembodiment.

FIG. 7 is a drawing of an exemplary LTE access gateway (LAG) inaccordance with an exemplary embodiment.

FIG. 8A is a drawing of a first part of an exemplary assembly ofcomponents, which may be included in a LTE access gateway (LAG) inaccordance with an exemplary embodiment. FIG. 8B is a drawing of asecond part of an exemplary assembly of components, which may beincluded in a LTE access gateway (LAG) in accordance with an exemplaryembodiment.

FIG. 8 comprises the combination of FIG. 8A and FIG. 8B.

FIG. 9 is a drawing of an exemplary LTE access database (LAD) inaccordance with an exemplary embodiment.

FIG. 10 is a drawing of an exemplary assembly of components, which maybe included in a LTE access database (LAD) in accordance with anexemplary embodiment.

DETAILED DESCRIPTION

FIG. 1 is a drawing of an exemplary communications system 100 inaccordance with an exemplary embodiment. Exemplary communications system100 includes an LTE network extension (LNE) system 102, a plurality ofservice provider core networks (service provider 1 (SP1) core network116, service provider 2 (SP2) core network 118, . . . , service providerN (SPN) core network 120), and a plurality of user equipment (UE)devices (UE 1A 122, UE2A 124, . . . , UEN1A 126, UE 1B 128, . . . ,UEN2B 130, UE 1C 132, UE2C 134, . . . , UEN3C 136).

LNE system 102 includes an LTE access gateway (LAG) 104, a plurality ofLTE access radios (LTE access radio (LAR) 1 106, LTE access radio (LAR)2 108, . . . , LTE access radio (LAR) M110), and a LTE access database(LAD) 112 coupled together. LAG 104 is coupled to the service providercore networks (SP1 core network 116, SP2 core network 118, . . . , SPNcore network 120), via communications links (146, 148, 150)respectively. LAG 104 is coupled to the LTE access radios (LAR 1 106,LAR 2 108, . . . , LAR M 110), via communications links (138, 140, . . ., 142), respectively. LAG 112 is coupled to LAD 112 via communicationslink 144.

UE devices (UE 1A 122, UE2A 124, . . . , UEN1A 126) are associated withservice provider 1 (SP1). UE devices (UE 1B 128, . . . , UEN2B 130) areassociated with service provider 2 (SP2). UE devices (UE 1C 132, UE2C134, . . . , UEN3C 136) are associated with service provider N (SPN).

Each of the LTE access radios (LAR 1 106, LAR 2 108, . . . , LAR M 110)broadcasts the same single PLMN, sometime referred to as a shared PLMN(sPLMN), which in this example is: 777-000. Service provider 1 (SP1)core network 116 corresponds to 310-001. Service provider 2 (SP2) corenetwork 118 corresponds to 311-002. Service provider N (SPN) corenetwork 120 corresponds to 312-00N.

LTE access database (LAD) 112 includes data/information 114 mappingsingle PLMN 777-000, corresponding to the set of LARs (106, 108, . . . ,110) in LNE system 102 to a plurality of different numbers (310-001,311-002, . . . , 312-00N) corresponding to different service providercore networks (SP1 core network 116, SP2 core network 118, . . . , SPMcore network 120).

Each of the LARs (LAR 1 106, LAR2 108, . . . , LAR M 110) transmitswireless signals (152, 156, 160) and receives wireless signals (154,158, . . . , 160), respectively. Each of the UE devices (UE 1A 122, UE2A124, . . . , UEN1A 126, UE 1B 128, . . . , UEN2B 130, UE 1C 132, UE2C134, . . . , UEN1C 136) transmits wireless signals (162, 166, . . . ,170, 174, . . . , 178, 182, 186, . . . , 190), and receives wirelesssignals (164, 168, . . . , 172, 176, . . . , 180, 184, . . . , 192),respectively.

LNE systems, e.g., LNE system 102, will broadcast a single shared PLMN,e.g. 777-000, using LTE access radios (LAR) in the LNE system, e.g., LAR1 106, LAR 2 108, . . . , LAR M 110 included in LNE system 102. Theseradios (LAR), e.g., LAR 1 106, LAR 2 108, LAR M 110, will be used toprovide services to participating service provider's subscribers.

A new novel component of novel LNE system is the LTE Access Gateway(LAG), e.g., LAG 104 of LTE 102. LAG, e.g., LAG 104, will control theaccess to LNE system, e.g., LNE system 102, and will act as a proxybetween LAR and target service provider network. LAG, e.g., LAG 104,will authenticate if the subscriber UE (user equipment), e.g., UE 1A122, requesting access to wireless network is allowed to access servicesbased on provisioned information in the LNE Access Database (LAD), e.g.,LAD 112. Once the access is authorized LAG will act as a transparentbridge between LTE radios and target service provider's core network.LAG will act as a core to LAR and as a radio (LAR) towards serviceprovider core network. LAD, e.g., LAD 112, will maintain a list ofparticipating (authorized) service providers, e.g., SP1 116, SP2 118, .. . , SP N 120, and their network access information (e.g. IP routing).

FIG. 2, comprising the combination of FIG. 2A, FIG. 2B and FIG. 2C, is adrawing of an exemplary signaling diagram 200, comprising part A 201,part B 203 and part C 205, in accordance with an exemplary embodiment.Signaling diagram 200 illustrates an exemplary LTE Network ExtensionCall Flow in accordance with an exemplary embodiment. Signaling diagram200 illustrates exemplary call flow information that will be used byvarious entities (network elements) to enable access to wirelessservices provided by the LNE system 102.

Signaling diagram 200 includes user equipment (UE) device 202, LTEnetwork extension (LNE) system 102 and service provider core network206. LAR 204 is, e.g., one of LAR 1 106, LAR 2 108, . . . , LAR M 110.UE device 202 is, e.g., one of the UEs (122, 124, . . . , 126, 128, . .. , 130, 132, 134, . . . , 136) of system 100 and service provider corenetwork 206 is, e.g., one of the service provider networks (116, 118, .. . , 120) of system 100. Service provider core network 206 is the homenetwork for UE 202. For example, in one embodiment, UE 202 is one of (UE1A 122, UE2A 124, . . . , UEN1A 126) and service provider network 206 isSP1 core network 116. In another embodiment, UE 202 is one of (UE 1B128, . . . , UEN2B 130) and service provider network 206 is SP2 corenetwork 118. In another embodiment, UE 202 is one of (UE 1C 132, UE 2C134, . . . , UEN3C 136) and service provider network 206 is SPN corenetwork 120.

Operation starts in step 208 in which the service provider home network206 provisions access to the home network extension (HNE) and updates UE202. Step 208 includes steps 210, which provisions the UE 202, and step216, which provisions the LAD 112. In step 210 the service provider corenetwork generates and sends UE provisioning signal 212 to UE 202. UEprovisioning signal 212 communicates a LNE system 102 PLMN ID as ashared PLMN (sPLMN) to enable access to the LNE system 102, whichincludes LAR 204. In step 214, UE 202 receives provisioning signal 212and recovers the communicated sPLMN ID. In step 210 the service providercore network 206 generates and sends LAD provisioning signals 218 to LAD112. LAD provisioning signals 218, in some embodiments, includes serviceprovider access information that includes target network addressinformation and a home PLMN ID for the UE (UE's service provider PLMNID). In various embodiments, the information communicated in LADprovisioning signals includes service provider core network accessinformation for a plurality of different service provider core networksassociated with a first shared PLMIN ID, e.g, 777-000, said serviceprovider core network access information including a PLMN ID of eachindividual service provider core network and corresponding addressinformation including for the individual service provider core networkfor which a PLMN is stored. For example, each of the service providercore networks 116, 118, . . . 120, may send a provisioning signal 218 toLAD 112. In step 220 LAD 112 receives message 218, recovers thecommunicated information. In step 221 LAD 112 stores the recoveredcommunicated information. When the provisioning signals from each of theservice provider core network are aggregated, the LAD 112 includesstored service provider core network access information including a PLMNID of each individual service provider core network and correspondingaddress information including for the individual service provider corenetwork for which a PLMN is stored.

In step 222, LAR 204 generates and transmits LAR broadcast message 224.LAR broadcast message 224 includes the LNE sPLMN ID, e.g., 777-000.Sometimes the LNE sPLMN ID is referred to as HNE sPLMN ID. In step 226UE 202 roams on to the LNE system 102, listens to broadcasts, receivesbroadcast message 224 and detects HNE sPLMN ID, e.g., detects 777-000.In step 228, UE 202 generates and sends an attach request message 230 toLAR 204, e.g., in response to having detected the shared PLMN ID. Theattach request message 230 includes the PLMN ID of the home network ofthe UE 202, e.g., as part of the IMSI. In step 232, LAR 204 receivesattach request 232. In step 234, LAR 204 forwards the received attachrequest message 230, as attach request message 236, to LAG 104. In step238 LAG 104 receives attach request message 236.

In step 240, LAG 104 stores the received attach request. In step 242 LAG104 decodes the service provider PLMN ID using the International MobileSubscriber Identity (IMSI) in the received attach request message.

In step 243 the LNE system 102 performs a service provider accessrequest check. Step 243 includes steps 244, 246, 248, 250, 252, and 258.In step 244, LAG 104 generates and sends a check service provider accessmessage 245 to LAD 112 requesting LAD 112 to check if the decoded PLMNis provisioned. In step 246 LAD 112 receives message 245 and recoversthe communicated information, and in step 248 LAD 112 checks itsdatabase to determine if the PLMN is provisioned. In step 250, LAD 112generates a response message 254, e.g., a PLMN allowed message or a PLMNnot allowed message, based on the determination of step 248. In step252, LAD 112 sends the generated response message 254 to LAG 104. Insome embodiments, in the case where response message 254 is a serviceprovider allowed message, e.g., PLMN, allowed message, response message254 includes target network access information, e.g., IP network routinginformation to set up a service flow.

In step 258, LAG receives response message 254 and recovers thecommunicated information.

In step 259 the LAG 104 determines if access is to be provided to UE 202based on the content of received response message. If the determinationof step 259 is that access is not to be provided, then operationproceeds from step 259 to step 259 a, in which the LAG 104 generates andsends deny access message 259 b to LAR 204, which receives message 259 bin step 259 c. However, if the determination of step 259 is that accessis to be provided, then operation proceeds from step 259 to step 259 d,in which LAG 104 generates a proxied attach request message 262 from thestored attach request. In step 260 LAG 104 uses IP network informationto set up connectivity (service flow) with the target provider networkand sends, the generated proxied attach request message 262, to serviceprovider core network 206. In step 264, the service provider corenetwork 206 receives proxied attach request message 262 and recovers thecommunicated information.

In step 266 the LAG 104 operates as a proxy between LAR 204 and serviceprovider 206 for further exchanges of control information and datato/from UE 202.

In step 268 service provider core network 206 authenticates the UE 202.In step 270, service provider core network 206 generates and sends UEattach accept signal 272 to UE 202. Attach accept signal 272 is receivedby UE 202, which recovers the communicated information. In step 276,service provider core network 206 generates and sends an end to endconnectivity (bearer) established signal 276 to UE 202. In step 278, UE202 receives signal 276 and recovers the communicated information. Instep 280 UE 202 determines that it is allowed to access home network 206over the LNE system 102 and performs normal LTE service operations.

In steps 282 and 284, the UE 202 and service provider core network 206are operated to interact including signaling 286 over the home networkextension 102, e.g., with LAG 104 serving as a proxy.

In one exemplary embodiment, UE 202 is UE 1A 122, service provider corenetwork 206 is SP1 core network 116, LTE access radio 204 is LAR 1 106,the shared PLMN (sPLMN) ID, which is broadcast is 777-000, and UE′ 202 shome network service provider core PLMN ID=310-001.

In another exemplary embodiment, UE 202 is UE 1B 128, service providercore network 206 is SP2 core network 118, LTE access radio 204 is LAR 2108, the shared PLMN (sPLMN) ID, which is broadcast is 777-000, and UE′202 s home network service provider core PLMN ID=311-002.

In another exemplary embodiment, UE 202 is UE 1C 132, service providercore network 206 is SPN core network 120, LTE access radio 204 is LAR 1106, the shared PLMN (sPLMN) ID, which is broadcast is 777-000, and UE′202 s home network service provider core PLMN ID=311-00N.

FIG. 3, comprising the combination of FIG. 3A, FIG. 3B, FIG. 3C, FIG. 3Dand FIG. 3E, is a drawing of an exemplary Attach Request message 300,comprising Part A 301, Part B 303, Part C 305, Part D 307, Part E 309and Part F 311, which is used by a LAG, e.g., LAG 104, to identifytarget PLMN (310-014).

FIG. 4, comprising the combination of FIG. 4A, FIG. 4B and FIG. 4C, is aflowchart 400 of an exemplary method of operating an LTE communicationssystem in accordance with an exemplary embodiment. The LTEcommunications system is, e.g., LTE communications system 100 of FIG. 1including LTE network extension system 102.

The exemplary method starts in step 402, in which the system is poweredon and initialized and proceeds to step 404. In step 404 serviceprovider core network access information for a plurality of differentservice provider core networks associated with a first shared PLMN ID isstored in a storage device, said service provider core network accessinformation including a PLMN ID of each individual service provider corenetwork and corresponding address information for the individual serviceprovider core network for which a PLMN ID is stored. Operation proceedsfrom step 404 to step 406.

In step 406 an LTE access radio (LAR) is operated to transmit, e.g., ina broadcast message, said first shared PLMN ID, e.g., 777-000. The LTEaccess radio is, e.g., one of LAT 1 106, LAR 2 108, . . . , LAR 110 ofFIG. 1 or LAR 204 of FIG. 2. Operation proceeds from step 406 to step408.

In step 408 the LTE access radio is operated to receive a first attachrequest from a first user equipment (UE) device, e.g., said first attachrequest having been transmitted by said first UE in response to saidfirst UE receiving said first shared PLMN ID. The UE device is, e.g. oneof UEs (122, 124, . . . , 126, 128, . . . , 130, 132, 134, . . . , 136)of FIG. 1 or UE 202 of FIG. 2. Operation proceeds from step 408 to step410.

In step 410 the LTE access radio is operated to forward the first attachrequest to a LTE access gateway, e.g., LAG 104. Operation proceeds fromstep 410 to step 412.

In step 412 the LTE access radio is operated to store the first attachrequest, said first attach request including a first IMSI of the firstUE device, said first IMSI including a first PLMN ID of an individualservice provider core network used to provide network access to thefirst UE, said first PLMN ID being a PLMN of a first target network,said first target network being one of said plurality of differentservice provider core networks, said first PLMN ID being different fromsaid shared PLMN ID. Operation proceeds from step 412, via connectingnode A 414, to step 416.

In step 416, the LTE network extension (LNE) system performs a serviceprovider access request check to determine if the LTE access radio is toprovide access service for the first target network identified by thefirst PLMN ID. Step 416 includes steps 420, 422, 424, and 434. In step420 the LTE access gateway sends a check service provider access messageto the storage device, e.g., LAD 122, including information ofindividual service provider core networks associated with the sharedPLMN ID for which access service is to be provided, said check serviceprovider access message including the first PLMN ID identifying thetarget service provider core network. Operation proceeds from step 420to step 422.

In step 422 the storage device is operated to check stored informationto determine if the first PLMN ID is a PLMN ID for which serviceprovider core network contact address information is provided. Operationproceeds from step 422 to step 424.

In step 424 the storage device generates a service provider accessrequest response message. Step 424 includes steps 426, 428, 432, and insome embodiments, step 430. In step 426 if the determination is that thecontact address information is provided in the stored information forthe first PLMN ID, then operation proceeds from step 426 to step 428;otherwise, operation proceeds from step 426 to step 432.

Returning to step 428, in step 428 the storage device includes theservice provider core network contact address information for the targetservice provider core network in the service provider access requestresponse message. In some embodiments, operation proceeds from step 428to optional step 430 in which an express access authorized indicator isincluded in said service provider access request response message. Inembodiments, in which step 430 is omitted, the inclusion of the serviceprovider core network address information in the response message isused to inform the LTE access gateway that the service provider requestresponse message is indicating access authorized.

Returning to step 432, in step 432 the storage device includes anindication that access is not allowed in the service provider accessrequest response message. Operation proceeds from step 424 to step 434.

In step 434, the storage device sends the generated service provideraccess request response message to the LTE access gateway, said serviceprovider access request response message indicating one of: i) access isallowed for the that target service provider core network identified bythe first PLMN ID or ii) access is not allowed.

Operation proceeds from step 418, via connecting node B 436, to step438. In step 438 the LTE access gateway is operated to receive theservice provider access request response message and recover theinformation communicated in the message. Operation proceeds from step438 to step 440.

In step 440, the LTE access gateway is operated to decide whether or notto provide access for the first UE device based on the content of theservice provider access request response message. Operation proceedsfrom step 440 to step 442.

In step 442, if the decision is a decision to provide access for thefirst UE, then operation proceeds from step 442 to step 444; however, ifthe decision is a decision to deny access for the first UE, thenoperation proceeds from step 442 to step 446.

In step 444, the LTE access gateway is operated to use IP networkaddress information corresponding to the first target network, receivedin the access request response message and stored information from thestored attach request that was received from the first UE to generate atthe LTE access gateway a proxied attach request message on behalf of thefirst UE. Operation proceeds from step 444 to step 448 in which the LTEaccess gateway sends the generated proxied attach request message to theservice provider core network corresponding to the first PLMN ID usingan address obtained from the access request response message as thedestination address of the proxied attach request message. Operationproceeds from step 448 to step 450.

In step 450, the LTE access gateway is operated to act as a proxybetween the LTE access radio and service provider core networkidentified by the first PLMN ID. Step 450 includes steps 452 and 454. Instep 452 the LTE access gateway is operated to communicate an attachaccept signal between the service provider network corresponding to thefirst PLMN and the first UE device. In step 454 the LTE access gatewayis operated to communicate an end to end bearer established signalbetween the service provider network corresponding to the first PLMN andthe first UE device.

Returning to step 446, in step 446, the LTE access gateway is operatedto send a message to LTE access radio to deny the UE access in responseto the first attach request message.

FIG. 5 is a drawing of an exemplary LTE access radio (LAR) 500 inaccordance with an exemplary embodiment. LTE access radios (LAR 1 106,LAR 2 108, . . . , LAR M 110) of FIG. 1 and LAR 204 of FIG. 2, are,e.g., LARs implemented in accordance with LAR 500 of FIG. 5.

LTE access radio 500 includes a processor 502, e.g., a CPU, an assemblyof components 504, e.g., an assembly of hardware components, e.g.,assembly of circuits, an I/O interface 506, a wireless interface 522,memory 512, an output device 514, e.g., a display, and an input device,e.g., a keyboard, mouse, etc., coupled together via a bus 517 via whichthe various components (502, 504, 506, 522, 512, 514, 516) may exchangedata and information. I/O interface 506 includes a receiver 508 and atransmitter 510, via which the LTE access radio 500 may receive signalsand send signals, e.g., from/to other devices, e.g., an LTE accessgateway. Wireless interface 522 includes a wireless receiver 524 and awireless transmitter 526. Wireless receiver 524 is coupled to receiveantenna 525, via which the LTE access radio may receive wirelesssignals, e.g., LTE wireless signals, from a UE device. Wirelesstransmitter 526 is coupled to transmit antenna 527, via which the LTEaccess radio may transmit wireless signals, e.g., LTE wireless signals,to a UE device. In some embodiments, the same antenna is used forreceiver 524 and transmitter 526. Memory 512 includes control routines517 configured to control operation of the various interfaces anddevices included in LAR 500, an assembly of components 518, e.g., anassembly of software components, and data/information 520.Data/information 520 includes a stored shared PLMN ID (sPLMN ID) 540,e.g., sPLMN ID=777-000, a generated broadcast message 542 includinginformation 544, which is a copy of the stored sPLMN ID 540, a receivedattach request message from a UE device 546, e.g., which was transmittedin response to the UE detecting the shared PLMN ID of broadcast message542, an a generated forwarded attach request message 548 directed to anLTE gateway.

FIG. 6 is a drawing of an exemplary assembly of components 600, whichmay be included in a LTE access radio (LAR) 500 in accordance with anexemplary embodiment. Assembly of components 600 can be, and in someembodiments is, used in LTE access radio (LAR) 500 of FIG. 5. Thecomponents in the assembly of components 600 can, and in someembodiments are, implemented fully in hardware within the processor 502,e.g., as individual circuits. The components in the assembly ofcomponents 600 can, and in some embodiments are, implemented fully inhardware within the assembly of components 504, e.g., as individualcircuits corresponding to the different components. In other embodimentssome of the components are implemented, e.g., as circuits, within theprocessor 502 with other components being implemented, e.g., as circuitswithin assembly of components 504, external to and coupled to theprocessor 502. As should be appreciated the level of integration ofcomponents on the processor and/or with some components being externalto the processor may be one of design choice. Alternatively, rather thanbeing implemented as circuits, all or some of the components may beimplemented in software and stored in the memory 512 of the LAR 500,with the components controlling operation of LAR 500 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 502. In some such embodiments,the assembly of components 600 is included in the memory 512 as assemblyof components 518. In still other embodiments, various components inassembly of components 600 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 502 which then under software controloperates to perform a portion of a component's function. While processor502 is shown in the FIG. 5 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 502 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 502, configure the processor 502 to implementthe function corresponding to the component. In embodiments where theassembly of components 600 is stored in the memory 512, the memory 512is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 502, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 6 control and/or configure the LTE access radio 500or elements therein such as the processor 502, to perform the functionsof corresponding steps illustrated and/or described in the method of oneor more of the flowcharts, signaling diagrams and/or described withrespect to any of the Figures. Thus the assembly of components 600includes various components that perform functions of corresponding oneor more described and/or illustrated steps of an exemplary method, e.g.,steps of the method of signaling diagram 200 of FIG. 2 and/or steps ofthe method of flowchart 400 of FIG. 4.

Assembly of components 600 includes a component 601 configured togenerate a message, e.g. a broadcast message, including a first sharedPLMN ID, a component 602 configured to operate an LTE access radio (LAR)to transmit a first shared PLMN ID, a component 604 configured tooperate an LTE access radio to receive a first attach request from afirst user equipment device, and a component 606 configured to operatethe LTE access radio to forward the first attach request to a LTE accessgateway. In various embodiemtns, component 602 is configured to controlthe LAR to transmit a broadcast message communicating the first sharedPLMN ID, e.g., on a recurring basis.

FIG. 7 is a drawing of an exemplary LTE access gateway (LAG) 700 inaccordance with an exemplary embodiment. LAG 700 is, e.g., LAG 104 ofFIG. 1 and FIG. 2. LTE access gateway 700 includes a processor 702,e.g., a CPU, an assembly of components 704, e.g., an assembly ofhardware components, e.g., assembly of circuits, an I/O interface 706,memory 712, an output device 714, e.g., a display, and an input device716, e.g., a keyboard, mouse, etc., coupled together via a bus 717 viawhich the various components (702, 704, 706, 712, 714, 716) may exchangedata and information. I/O interface 706 includes a receiver 708 and atransmitter 710, via which the LTE access gateway 700 may receivesignals and send signals, e.g., from/to other devices, e.g., an LTEaccess database, an LTE access radio, devices in a service provider corenetwork, etc. Memory 712 includes control routines 714, which controlvarious functions and operations of the interfaces and devices includedin LAG 700, an assembly of components 718, e.g., an assembly of softwarecomponents, and data/information 720. Data/information 720 includes astored received attach request message 722, a decoded service providerPLMN ID 724 from the IMSI included the received attach request message,a generated check service provider access message 726, and a receivedservice provider access request response message 728, which includeswhen access is allowed, service provider core network IP addressinformation, an access decision 732. Data/information 720 includes,e.g., for the case in which the access request response is accessallowed, a generated proxied attach request message 734, an attachaccept signal 738, which is being forwarded while the LAG 700 is servingas a proxy, and an end to end bearer established signal 740, which isbeing forwarded while the LAG is serving as a proxy. Data/information720 includes, e.g., for the case in which the access request responsecommunicates access denied, a generated access denied message 736, whichis to be sent to the access radio.

FIG. 8, comprising the combination of FIG. 8A and FIG. 8B, is a drawingof an exemplary assembly of components 800, comprising the combinationof Part A 801 and Part B 803, which may be included in a LTE accessgateway (LAG) 800 in accordance with an exemplary embodiment. Assemblyof components 800 can be, and in some embodiments is, used in LTE accessgateway (LAG) 700 of FIG. 7. The components in the assembly ofcomponents 800 can, and in some embodiments are, implemented fully inhardware within the processor 702, e.g., as individual circuits. Thecomponents in the assembly of components 800 can, and in someembodiments are, implemented fully in hardware within the assembly ofcomponents 704, e.g., as individual circuits corresponding to thedifferent components. In other embodiments some of the components areimplemented, e.g., as circuits, within the processor 702 with othercomponents being implemented, e.g., as circuits within assembly ofcomponents 704, external to and coupled to the processor 702. As shouldbe appreciated the level of integration of components on the processorand/or with some components being external to the processor may be oneof design choice. Alternatively, rather than being implemented ascircuits, all or some of the components may be implemented in softwareand stored in the memory 712 of the LAG 700, with the componentscontrolling operation of LAG 700 to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 800 is included in the memory 712 as assembly ofcomponents 718. In still other embodiments, various components inassembly of components 800 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 800 is stored in the memory 712, the memory 712is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 8 control and/or configure the LTE access gateway700 or elements therein such as the processor 702, to perform thefunctions of corresponding steps illustrated and/or described in themethod of one or more of the flowcharts, signaling diagrams and/ordescribed with respect to any of the Figures. Thus the assembly ofcomponents 800 includes various components that perform functions ofcorresponding one or more described and/or illustrated steps of anexemplary method, e.g., steps of the method of signaling diagram 200 ofFIG. 2 and/or steps of the method of flowchart 400 of FIG. 4.

Assembly of components 800 includes a component 802 configured tooperate the LTE access gateway to receive the forwarded first attachrequest from the LTE access radio, and a component 804 configured tooperate the LTE access gateway to store the first attach request, saidfirst attach request including a first IMSI of the first UE deviceincluding a first PLMN ID of an individual service provider core networkused to provide network access to the first UE, said first PLMN ID beinga PLMN ID of a first target network, said first target network being oneof said plurality of different service provider core networks, saidfirst PLMN ID being different from said shared PLMN ID. Assembly ofcomponents 800 further includes a component 806 configured to perform aservice provider access request check to determine if the LTE accessradio is to provide access service for the first target networkidentified by the first PLMN ID. Component 806 includes a component 807configured to generate a check service provider access message, and acomponent 808 configured to send a check service provider access messageto a storage device, e.g., a LTE access database, including informationof the individual service provider core networks associated with theshared PLMN ID for which access service is to be provided, said checkservice provider access message including the first PLMN ID identifyingthe target service provider core network. Assembly of components 800further comprises a component 810 configured to operate the LTE gatewaydevice to receive a service provider access request response message andrecover the information communicated in the message, a component 812configured to operate the LTE access gateway to decide whether or not toprovide access for the first UE based on the content of the receivedservice provider access request response message, and a component 814configured to control operation as a function of the decision whether ornot to provide access for the first UE. Assembly of components 800further includes a component 816 configure to operate the LTE accessgateway to use IP network address information corresponding to the firsttarget network, received in the access request response messaged and thestored attach request that was received from the first UE to generate atthe LTE access gateway a proxied attach request message on behalf of thefirst UE, e.g., in response to a receiving access request responsemessage communicating, e.g., indirectly via the including of IP networkaddress information or directly via an access allowed indicator, thataccess is allowed, and a component 818 configured to operate the LTEaccess gateway to generate and send a message to LTE access radio todeny the UE access in response to the first attach request message,e.g., in response to receiving an access request response messageindicating access is denied. Assembly of components 800 further includesa component 820 configured to send the generated proxied attach requestmessage to the service provider core network corresponding to the firstPLMN ID as the destination address of the proxied attach requestmessage, and a component 822 configured to operate the LTE accessgateway to act as a proxy between the LTE access radio and the serviceprovider core network identified by the first PLMN ID. Component 822includes a component 824 configured to operate the LTE access gateway tocommunicate an attach accept signal between the service provider networkcorresponding to the first PLMN ID and the first UE device and acomponent 826 configured to operate the LTE access gateway tocommunicate an END to END bearer established signal between the serviceprovider network corresponding to the first PLMNID and the first UEdevice.

FIG. 9 is a drawing of an exemplary storage device, e.g., an LTE accessdatabase (LAD), 900 in accordance with an exemplary embodiment. LAD 900is, e.g., LAD 112 of FIG. 1 and FIG. 2. LTE access database 900 includesa processor 902, e.g., a CPU, an assembly of components 904, e.g., anassembly of hardware components, e.g., assembly of circuits, an I/Ointerface 906, memory 912, an output device 914, e.g., a display, and aninput device 916, e.g., a keyboard, mouse, etc., coupled together via abus 917 via which the various components (902, 904, 906, 912, 914, 916)may exchange data and information. I/O interface 906 includes a receiver908 and a transmitter 910, via which the LTE access database 900 mayreceive signals and send signals, e.g., from/to other devices, e.g., anLTE access gateway, a device in a service provider core network, etc.Memory 912 includes control routines 917 configured to control functionand operation of the various interfaces and devices included in LAD 900,an assembly of components 918, e.g., an assembly of software components,and data/information 920. Data/information 920 includes receivedmessages 922 communicating provisioning information 922, storedprovisioning information 924, a received check service provider accessmessage 940, a generated service provider request response message 942,and a billing information table 943. The stored provisioning information924 includes a shared PLMN ID (sPLMN ID), e.g., 777-000, and informationcorresponding to a plurality of service provider core networks, whichcorrespond to the shared PLMN ID 926. The information corresponding tothe plurality of service provider core networks, which correspond to theshared PLMN ID 926, includes: service provider 1 core networkinformation including a service provider 1 core network 1 PLMN ID 928,e.g., 310-001, and service provider 1 core network IP addressinformation 924; service provider 2 core network information including aservice provider 2 core network PLMN ID 930, e.g., 311-002, and serviceprovider 2 core network IP address information 936; . . . ; serviceprovider N core network information including a service provider N corenetwork PLMN ID 932, e.g., 312-00N, where N is an integer value in therange of 0 . . . 9, and service provider N core network IP addressinformation 938. In some embodiments the stored provisioning information924 is included in an access table 925.

FIG. 10 is a drawing of an exemplary assembly of components 1000, whichmay be included in a LTE access database (LAD) 900 in accordance with anexemplary embodiment. Assembly of components 1000 can be, and in someembodiments is, used in LTE access database (LAD) 900 of FIG. 9. Thecomponents in the assembly of components 1000 can, and in someembodiments are, implemented fully in hardware within the processor 902,e.g., as individual circuits. The components in the assembly ofcomponents 1000 can, and in some embodiments are, implemented fully inhardware within the assembly of components 904, e.g., as individualcircuits corresponding to the different components. In other embodimentssome of the components are implemented, e.g., as circuits, within theprocessor 902 with other components being implemented, e.g., as circuitswithin assembly of components 904, external to and coupled to theprocessor 902. As should be appreciated the level of integration ofcomponents on the processor and/or with some components being externalto the processor may be one of design choice. Alternatively, rather thanbeing implemented as circuits, all or some of the components may beimplemented in software and stored in the memory 912 of the LAD 900,with the components controlling operation of LAD 900 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 902. In some such embodiments,the assembly of components 1000 is included in the memory 912 asassembly of components 918. In still other embodiments, variouscomponents in assembly of components 1000 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 902 whichthen under software control operates to perform a portion of acomponent's function. While processor 902 is shown in the FIG. 9embodiment as a single processor, e.g., computer, it should beappreciated that the processor 702 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 902, configure the processor 902 to implementthe function corresponding to the component. In embodiments where theassembly of components 1000 is stored in the memory 912, the memory 912is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 902, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 8 control and/or configure the LTE access database900 or elements therein such as the processor 902, to perform thefunctions of corresponding steps illustrated and/or described in themethod of one or more of the flowcharts, signaling diagrams and/ordescribed with respect to any of the Figures. Thus the assembly ofcomponents 1000 includes various components that perform functions ofcorresponding one or more described and/or illustrated steps of anexemplary method, e.g., steps of the method of signaling diagram 200 ofFIG. 2 and/or steps of the method of flowchart 400 of FIG. 4.

Assembly of components 1000 includes a component 1002 configured tostore in a stored device service provider core network accessinformation for a plurality of different service provider core networksassociated with a first shared PLMN ID, said service provider corenetwork access information including a PLMN if each individual serviceprovider core network and corresponding address information for theindividual service provider core network for which a PLMN ID is stored,and a component configured to perform a service provider access requestcheck to determine if the LTE access radio is to provide access servicefor the first target network identified by the first PLMN ID.

Component 1004 includes a component 1006 configured to receive a checkservice provider access message including the first PLMN ID identifyingthe target service provider core network a component 1008 configured tooperate the storage device to check stored information to determine ifthe first PLMN ID is a PLMN ID for which service provider core networkcontact address information is provided, a component 1010 configured togenerate a service provider access request response message at thestorage device, and a component 1020 configured to send from the storagedevice, e.g., to a LTE access gateway, a service provider access requestresponse message, said service provider access request response messageindicating one of: i) access is allowed for the target service providercore network identified by the first PLMN ID or ii) access is notallowed.

Component 1010 includes a component 1012 configured to control operationas a function of the determination if contact address information isprovided in the stored information for the first PLMN ID, a component1014 configured to include the service provider core network contactaddress information for the target service provider core network in theservice provider access request response message, e.g., in response to adetermination that contact information is provided and that access is tobe granted, and a component 1018 configured to include an indicationthat access is not allowed in the service provider access requestresponse, e.g., in response to a determination that the first PLMN ID isnot a PLMN ID for which service provider network contact addressinformation is provided and that access is denied. In some embodiments,component 1010 further includes a component 1016 configured to includean express access authorized indicator in said service provider accessrequest response message, e.g., when access is to be allowed.

Various aspects and/or features of some embodiments of the presentinvention are further described below. New service providers can buildLNE system architecture based networks, in accordance with featuresand/or aspects of the present invention to extend the wireless servicesto other service providers that do not have coverage. These smallservice provider systems can complement each other's networks to provideservices to their customers in the new areas.

The LTE network extension system is a new way of providing wirelessservices to the subscribers of affiliated LTE based wireless serviceproviders. In some embodiments, an LTE network extension system is athird party solution, e.g., with a third party owning and/or controllingthe LTE network extension system infrastructure, e.g., which is rentedand/or leased out to one or more service providers. In some embodiments,an LTE network extension system is build and/or owned by one of theservice providers and extended services are offered to other serviceproviders, e.g., on a fee basis. The availability of LTE networkextension systems will help wireless service providers to extend theirnetwork coverage and can also save cost of building new coverage areas.

Exemplary LTE network extension systems, in accordance with variousfeatures and/or aspects of the present invention, will overcome some thelimitations with the current solutions to encourage the proliferation ofsmall service providers that will be able to roam onto partner networkswithout complicated network set up.

Some of the benefits of LNE system(s), implemented in accordance withthe present invention, include one or more of the following. An LTENetwork extension system can, and sometimes does, extends LTE servicewithout extensive roaming arrangement providing ease of provisioning andsign up. An LTE Network extension system overcomes the 6 network limitof MOCN architecture since number of supported partners is unlimited.Small network will be able to sign up to use these LNE networks and willencourage build of new wireless networks. An LNE system can be, andsometimes is, used to offload the macro network by large serviceproviders in the hot spots, e.g., highly utilized areas e.g. venues,downtown, heavily populated areas. This will help large serviceproviders to save cost of building network and also provide better userexperience on LNE system which are expected to offer more capacity.

In some embodiments, an LNE system will broadcast a single PLMN (e.g.777-000), sometimes referred to as a shared PLMN ID (sPLMN ID) using aset of LTE access radios (LAR). These radios (LAR) will be used toprovide services to participating service provider's subscribers.Different LNE systems may, and sometimes do, correspond to differentshared PLMN IDs.

A novel component of various exemplary LNE systems is the LTE AccessGateway (LAG). The LAG will control the access to LNE system and willact as a proxy between LAR and target service provider network. In someembodiments, the LAG will authenticate if the subscriber UE (userequipment) requesting access to wireless network is allowed to accessservices based on provisioned information in the LNE Access Database(LAD). In various embodiments, once the access is authorized, the LAGwill act as a transparent bridge between LTE radios and target serviceprovider's core network. In some embodiments, the LAG will act as a coreto LAR and as a radio (LAR) towards service provider core network. Insome embodiments, the LAD will maintain a list of participating(authorized) service providers and their network access information(e.g. IP routing).

The exemplary novel LNE system 102 architecture of LTE system 100 ofFIG. 1 includes two new novel network elements called a LNE AccessGateway (LAG) 104 and a LNE Access Database (LAD) 112 in the LTE networkarchitecture.

Exemplary new signaling messages, in accordance with some embodiments,include:

-   -   (i) a message from a Service provider to provision LAD for        access, e.g., LAD provisioning signal message 218 of FIG. 2;    -   (ii) a message from the LAG to LAD to check if a service        provider is provisioned, e.g., check service provider access        message 245 from LAG 104 to LAD 112; and    -   (iii) a message from the LAD to the LAG to respond to LAG and        notify the LAG if the service provider is provisioned along with        data routing information to set up connectivity (service flow)        if the service provider is provisioned, e.g., response message        254 from LAD 112 to LAG 104.

In various embodiments, a service provider provisions access to the LNEsystem via a message sent to the LAD. An exemplary Provision LTE networkextension system for Access messages, in accordance with someembodiments, includes messages with the following features, informationand/or characteristics:

-   -   Message Type: SUBSCRIBE FOR ACCESS        -   PLMN        -   Evolved Packet Core Access Information            -   IP Addresses    -   Message Type: SUBSCRIBE FOR ACCESS ACKNOWLEDGEMENT        -   Success

An Exemplary LAG to LAD Check Servicer Provider Access Message, inaccordance with some embodiments, includes the the following features,information and/or characteristics:

-   -   Message Type: CHECK SERVICE PROVIDER ACCESS        -   PLMN

An exemplary LAD to LAG Service Provider Access Response Message, inaccordance with some embodiments, includes the the following features,information and/or characteristics:

-   -   Message Type: SERVICE PROVIDER ACCESS RESPONSE        -   PLMN ALLOWED            -   PLMN EPC Access Information            -   IP addresses    -   Message Type: SERVICE PROVIDER ACCESS RESPONSE        -   PLMN NOT ALLOWED

An exemplary LAG Database, e.g., LAD 112, structure, in accordance withsome embodiments, will now be described. In various embodiments, the LAGdatabase, e.g., LAD 112, includes access and billing relatedinformation, e.g., as shown below.

In some embodiments, an access table is provisioned to authenticateallowed PLMN and network access information for example IP addresses. Insome embodiments, a billing table is used to maintain LNE Systemutilization by PLMN and subscriber ID along with session type, durationand amount of data exchanged during the session.

Access PLMN IP Addresses Billing PLMN Subscriber ID Session Type SessionDuration Data volume

Numbered List of Exemplary Method Embodiments

Method Embodiment 1 A method of operating an LTE communications system(100), the method comprising: storing (221) in a storage device (LAD112) service provider core network access information for a plurality ofdifferent service provider core networks associated with a first sharedPLMN ID (sPLMN ID) (e.g., service provider core network accessinformation for, in some embodiments more than 6, different serviceprovider core networks may be stored, which may be used when an attachrequest is received including a first shared PLMN ID used to supportproviding of service to a plurality of different individual serviceprovider core networks), said service provider core network accessinformation including a PLMN ID of each individual service provider corenetwork and corresponding address information (e.g., an IP address to beused to contact an individual service provider core network) for theindividual service provider core network for which a PLMN ID is stored;operating an LTE access radio (204) to transmit (222), (e.g., in abroadcast message,) said first shared PLMN ID; and operating the LTEaccess radio (204) to receive (232) a first attach request (230) from afirst user equipment (UE) device (202), (e.g., said first attach requesthaving been transmitted by the first UE in response to the first UEreceiving the first shared PLMN ID).

Method Embodiment 2 The method of Method Embodiment 1, furthercomprising: operating the LTE access radio (204) to forward (234) thefirst attach request to a LTE access gateway (104).

Method Embodiment 3 The method of Method Embodiment 2, furthercomprising: operating the LTE access gateway (104) to store (240) (e.g.,in memory 712) the first attach request, said first attach requestincluding a first IMSI of the first UE device (202) including a firstPLMN ID of an individual service provider core network (206) used toprovide network access to the first UE (202), said first PLMN ID being aPLMN ID of a first target network (206), said first target network beingone of said plurality of different service provider core networks, saidfirst PLMN ID being different from said shared PLMN ID; and perform(243) a service provider access request check (step 245 includesgenerating a check LAD message including the first PLMN ID extractedfrom the messages to the LAD) to determine if the LTE access radio (204)is to provide access service for the first target network identified bythe first PLMN ID.

Method Embodiment 4 The method of Method Embodiment 3, whereinperforming (243) a service provider access request check (245) includes:sending (244) a check service provider access message (245) to thestorage device (LAD 112) including information on individual serviceprovider core networks associated with the shared PLMN ID for whichaccess service is to be provided, said check service provider accessmessage (245) including the first PLMN ID identifying the target serviceprovider core network; operating the storage device (LAD 112) to check(248) stored information to determine if the first PLMN ID is a PLMN IDfor which service provider core network contact address information isprovided (which will be the case if service is provisioned for thetarget service provider core network identified by the first PLMN ID);and sending (252) from the storage device (LAD 112) a service provideraccess request response message (254), said service provider accessrequest access request response message (254) indicating one of: i)access is allowed for the target service provider core networkidentified by the first PLMN ID or ii) access is not allowed.

Method Embodiment 5 The method of Method Embodiment 4, furthercomprising: prior to sending (252) the service provider access requestresponse message (254), generating (250) said service provider accessrequest response message (254) at said storage device (112), said stepof generating (250) said service provider access request responsemessage (254) including: i) when contact address information is providedin the stored information for the first PLMN ID, including the serviceprovider core network contact address information for the target serviceprovider core network in said service provider access request responsemessage (254) (in some embodiments the presence of such contact addressinformation in the response message indicates that access is authorized;while in other embodiments an express access authorized indicator isincluded in the response message in addition to the access networkcontact address information); and ii) when contact address informationis not provided in the stored information for the first PLMN ID (e.g.,because the LAR is not a shared host for the target service providernetwork), including in said service provider access request responsemessage (254) an indication that access is not allowed.

Method Embodiment 6 The method of Method Embodiment 5, furthercomprising: operating the LTE access gateway (104) to decide (259)whether or not to provide access for the first UE based on the contentof the service provider access request response message (254).

Method Embodiment 7 The method of Method Embodiment 6, furthercomprising: when the decision (259) is to provide access for the firstUE, operating (260) the LTE access gateway (104) to use IP networkaddress information corresponding to the first target network, receivedin the access request response message (254) and stored information fromthe stored attach request that was received from the first UE (202) togenerate (259 d), at the LTE access gateway (104), a proxied attachrequest message (262) on behalf of the first UE (202); send (260) theproxied attach request message (262) to the service provider corenetwork (206) corresponding to the first PLNM ID using an addressobtained from the access request response message (254) as thedestination address of the proxied attach request response message(262).

Method Embodiment 8 The method of Method Embodiment 7, furthercomprising: operating (266) the LTE access gateway to act as a proxybetween the LTE access radio 204 and service provider core network (206)identified by the first PLMN ID for further exchange of controlinformation and data on behalf of the first UE (202) as part ofproviding network access.

Method Embodiment 9 The method of Method Embodiment 8, wherein operating(266) the LTE access gateway to act as a proxy between the LTE accessradio (204) and service provider core network (206) identified by thefirst PLMN ID includes: operating the LTE access gateway (104) tocommunicate an attach accept signal (272) and an end to end bearerestablished signal (276) between the service provider network (206)corresponding to the first PLMN ID and the first UE (202).

Method Embodiment 10 The method of Method Embodiment 7, furthercomprising: when the decision (259) is to not provide access for thefirst UE (202), operating (259 a) the LTE access gateway (104) to send amessage (259 b) to the LTE access radio (204) to deny the UE (202)access in response to the first attach request message.

Numbered List of Exemplary System Embodiments

System Embodiment 1 An LTE communications system (100) comprising: astorage device (LAD 112) including memory (912) storing service providercore network access information for a plurality of different serviceprovider core networks associated with a first shared PLMN ID (sPLMN ID)(e.g., service provider core network access information for more than 6different service provider core networks, in some embodiments, may bestored, which may be used when an attach request is received including afirst shared PLMN ID used to support providing of service to a pluralityof different individual service provider core networks), said serviceprovider core network access information including a PLMN ID of eachindividual service provider core network and corresponding addressinformation (e.g., an IP address to be used to contact an individualservice provider core network) for the individual service provider corenetwork for which a PLMN ID is stored; an LTE access radio (204)including a first processor (502) configured to operate the LTE accessradio (204) to transmit (222) said first shared PLMN ID; and operate theLTE access radio (204) to receive (232) a first attach request (230)from a first user equipment (UE) device (202).

System Embodiment 2 The LTE communications system (100) of SystemEmbodiment 1, further comprising an LTE access gateway (104); andwherein said first processor (502) is further configured to: operate theLTE access radio (204) to forward (234) the first attach request to anLTE access gateway (104).

System Embodiment 3 The LTE communications system (100) of SystemEmbodiment 12, wherein said LTE access gateway (104) includes a secondprocessor (702), and wherein said second processor (702) is configuredto: operate the LTE access gateway (104) to store (240) (e.g., in memory712) the first attach request, said first attach request including afirst IMSI of the first UE device (202) including a first PLMN ID of anindividual service provider core network (206) used to provide networkaccess to the first UE (202), said first PLMN ID being a PLMN ID of afirst target network (206), said first target network being one of saidplurality of different service provider core networks, said first PLMNID being different from said shared PLMN ID; and operate LTE accessgateway (104) to perform (243) a service provider access request check(step 245 includes generating a check LAD message including the firstPLMN ID extracted from the messages to the LAD) to determine if the LTEaccess radio (204) is to provide access service for the first targetnetwork identified by the first PLMN ID.

System Embodiment 4 The LTE communications system (100) of SystemEmbodiment 3, wherein said second processor (702) is configured to: send(244) a check service provider access message (245) to the storagedevice (LAD 112) including information on individual service providercore networks associated with the shared PLMN ID for which accessservice is to be provided, said check service provider access message(245) including the first PLMN ID identifying the target serviceprovider core network, as part of being configured to perform a serviceprovider access request check; and wherein said storage device (112)includes a third processor (902), and wherein said third processor (902)is configured to: operate the storage device (LAD 112) to check (248)stored information to determine if the first PLMN ID is a PLMN ID forwhich service provider core network contact address information isprovided (which will be the case if service is provisioned for thetarget service provider core network identified by the first PLMN ID);and operate the storage device (LAD 112) to send (252) from the storagedevice (LAD 112), e.g., to the LTE access gateway, a service provideraccess request response message (254), said service provider accessrequest access request response message (254) indicating one of: i)access is allowed for the target service provider core networkidentified by the first PLMN ID or ii) access is not allowed.

System Embodiment 5 The LTE communications system (100) of SystemEmbodiment 14, wherein said third processor (902) is further configuredto: generate (250) said service provider access request response message(254) at said storage device (112) prior to sending (252) the serviceprovider access request response message (254), said step of generating(250) said service provider access request response message (254)including: i) when contact address information is provided in the storedinformation for the first PLMN ID, including the service provider corenetwork contact address information for the target service provider corenetwork in said service provider access request response message (254)(in some embodiments the presence of such contact address information inthe response message indicates that access is authorized; while in otherembodiments an express access authorized indicator is included in theresponse message in addition to the access network contact addressinformation); and ii) when contact address information is not providedin the stored information for the first PLMN ID (e.g., because the LARis not a shared host for the target service provider network), includingin said service provider access request response message (254) anindication that access is not allowed.

System Embodiment 6 The LTE communications system (100) of SystemEmbodiment 5, wherein said second processor (702) is further configuredto operate the LTE access gateway (104) to decide (259) whether or notto provide access for the first UE based on the content of the serviceprovider access request response message (254).

System Embodiment 7 The LTE communications system (100) of SystemEmbodiment 6, wherein said second processor (702) is further configuredto: operate (260) the LTE access gateway (104) to use IP network addressinformation corresponding to the first target network, received in theaccess request response message (254) and stored information from thestored attach request that was received from the first UE (202) togenerate (259 d), at the LTE access gateway (104), a proxied attachrequest message (262) on behalf of the first UE (202), when the decision(259) is to provide access for the first UE; and operate the LTE gatewaydevice (104) to send (260) the proxied attach request message (262) tothe service provider core network (206) corresponding to the first PLNMID using an address obtained from the access request response message(254) as the destination address of the proxied attach request responsemessage (262), when the decision (259) is to provide access for thefirst UE.

System Embodiment 8 The LTE communications system of System Embodiment7, wherein said second processor (702) is further configured to: operate(266) the LTE access gateway (104) to act as a proxy between the LTEaccess radio (204) and service provider core network (206) identified bythe first PLMN ID for further exchange of control information and dataon behalf of the first UE (202) as part of providing network access.

System Embodiment 9 The LTE communications system (100) of SystemEmbodiment 8, wherein said second processor (702) is further configuredto: operate the LTE access gateway (104) to communicate an attach acceptsignal (272) and an end to end bearer established signal (276) betweenthe service provider network (206) corresponding to the first PLMN IDand the first UE (202), as part of being configured to operate (266) theLTE access gateway to act as a proxy between the LTE access radio (204)and service provider core network (206) identified by the first PLMN ID.

System Embodiment 10 The LTE communications system (100) of SystemEmbodiment 7, wherein said second processor (702) is further configuredto: operate (259 a) the LTE access gateway (104) to send a message (259b) to the LTE access radio (204) to deny the UE (202) access in responseto the first attach request message, when the decision (259) is to notprovide access for the first UE (202).

System Embodiment 11 The LTE communications system (100) of SystemEmbodiment 2, wherein said LTE access radio (204), said LTE accessgateway (104) and said storage device (LAD 112) are part of an LTEnetwork extension (LNE) system (102).

System Embodiment 12 The LTE communications system (100) of SystemEmbodiment 11, wherein said LTE access radio (204) is one of at least 7LTE access radios (LAR 1 106, LAR 2 108, . . . . LAR M110, where M isgreater than or equal to 7) in the LTE network extension system (102)which broadcast the same shared PLMN ID (e.g., 777-000).

System Embodiment 13 The LTE communications system (100) of SystemEmbodiment 12, wherein said plurality of different service provider corenetworks associated with a first shared PLMN ID includes at least 7different service provider core networks.

Numbered List of Exemplary Computer Readable Medium Embodiments

Computer Readable medium Embodiment 1. A non-transitory computerreadable medium including computer executable instructions which whenexecuted by one or more processors of a LTE communications system causethe LTE ommunications system to perform the steps of: storing (221) in astorage device (LAD 112) service provider core network accessinformation for a plurality of different service provider core networksassociated with a first shared PLMN ID (sPLMN ID) (e.g., serviceprovider core network access information for more than 6 differentservice provider core networks, in some embodiments, may be stored,which may be used when an attach request is received including a firstshared PLMN ID used to support providing of service to a plurality ofdifferent individual service provider core networks), said serviceprovider core network access information including a PLMN ID of eachindividual service provider core network and corresponding addressinformation (e.g., an IP address to be used to contact an individualservice provider core network) for the individual service provider corenetwork for which a PLMN ID is stored; operating an LTE access radio(204) to transmit (222) said first shared PLMN ID; and operating the LTEaccess radio (204) to receive (232) a first attach request (230) from afirst user equipment (UE) device (202).

The techniques of various embodiments may be implemented using software,hardware and/or a combination of software and hardware. Variousembodiments are directed to apparatus and/or systems, a wirelesscellular LTE communications system, e.g., a 3GPP cellular systemincluding LTE/NR wireless access components and using fiber for at leasta portion of the backhaul, an LTE network extension system, serviceprovider core networks, core network components, a data network, accesspoints, e.g., 3GPP LT/NR access points, e.g., an LTE access radio, a LTEaccess gateway, a LTE access database, networks, a 4G LTE system, a 5GLTE system, etc. Various embodiments are also directed to methods, e.g.,method of controlling and/or operating a system or device, e.g., acommunications system, a LTE network extension system, a hybrid system,e.g., a hybrid cable/LTE system, etc. Various embodiments are alsodirected to machine, e.g., computer, readable medium, e.g., ROM, RAM,CDs, hard discs, etc., which include machine readable instructions forcontrolling a machine to implement one or more steps of a method. Thecomputer readable medium is, e.g., non-transitory computer readablemedium.

It is understood that the specific order or hierarchy of steps in theprocesses and methods disclosed is an example of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes and methods may be rearrangedwhile remaining within the scope of the present disclosure. Theaccompanying method claims present elements of the various steps in asample order, and are not meant to be limited to the specific order orhierarchy presented. In some embodiments, one or more processors areused to carry out one or more steps of the each of the describedmethods.

In various embodiments each of the steps or elements of a method areimplemented using one or more processors. In some embodiments, each ofelements are steps are implemented using hardware circuitry.

In various embodiments nodes and/or elements described herein areimplemented using one or more components to perform the stepscorresponding to one or more methods, for example, performingauthentication, identifying, generating a message, message reception,signal processing, sending, communicating, e.g., receiving andtransmitting, comparing, negotiating, making a decision, determiningand/or transmission steps. Thus, in some embodiments various featuresare implemented using components or in some embodiments logic such asfor example logic circuits. Such components may be implemented usingsoftware, hardware or a combination of software and hardware. Many ofthe above described methods or method steps can be implemented usingmachine executable instructions, such as software, included in a machinereadable medium such as a memory device, e.g., RAM, floppy disk, etc. tocontrol a machine, e.g., general purpose computer with or withoutadditional hardware, to implement all or portions of the above describedmethods, e.g., in one or more nodes. Accordingly, among other things,various embodiments are directed to a machine-readable medium, e.g., anon-transitory computer readable medium, including machine executableinstructions for causing a machine, e.g., processor and associatedhardware, to perform one or more of the steps of the above-describedmethod(s). Some embodiments are directed to a device, e.g., user devicesuch as a UE, a LTE access radio, a LTE access gateway, an LTE accessdatabase, a core device, a server, a communication node, etc., includinga processor configured to implement one, multiple or all of the steps ofone or more methods of the invention.

In some embodiments, the processor or processors, e.g., CPUs, of one ormore devices, are configured to perform the steps of the methodsdescribed as being performed by the devices, e.g., communication nodes.The configuration of the processor may be achieved by using one or morecomponents, e.g., software components, to control processorconfiguration and/or by including hardware in the processor, e.g.,hardware components, to perform the recited steps and/or controlprocessor configuration. Accordingly, some but not all embodiments aredirected to a device, e.g., communications node such as a UE, LTE accessradio, LTE access gateway, LTE access database, with a processor whichincludes a component corresponding to each of the steps of the variousdescribed methods performed by the device in which the processor isincluded. In some but not all embodiments a device, e.g., communicationsnode such as a LTE access radio, LTE access gateway, LTE accessdatabase, UE, service provider core node, includes a componentcorresponding to each of the steps of the various described methodsperformed by the device in which the processor is included. Thecomponents may be implemented using software and/or hardware.

Some embodiments are directed to a computer program product comprising acomputer-readable medium, e.g., a non-transitory computer-readablemedium, comprising code for causing a computer, or multiple computers,to implement various functions, steps, acts and/or operations, e.g. oneor more steps described above. Depending on the embodiment, the computerprogram product can, and sometimes does, include different code for eachstep to be performed. Thus, the computer program product may, andsometimes does, include code for each individual step of a method, e.g.,a method of controlling a controller or node. The code may be in theform of machine, e.g., computer, executable instructions stored on acomputer-readable medium, e.g., a non-transitory computer-readablemedium, such as a RAM (Random Access Memory), ROM (Read Only Memory) orother type of storage device. In addition to being directed to acomputer program product, some embodiments are directed to a processorconfigured to implement one or more of the various functions, steps,acts and/or operations of one or more methods described above.Accordingly, some embodiments are directed to a processor, e.g., CPU,configured to implement some or all of the steps of the methodsdescribed herein. The processor may be for use in, e.g., acommunications device such as a controller or other device described inthe present application.

Numerous additional variations on the methods and apparatus of thevarious embodiments described above will be apparent to those skilled inthe art in view of the above description. Such variations are to beconsidered within the scope. Numerous additional embodiments, within thescope of the present invention, will be apparent to those of ordinaryskill in the art in view of the above description and the claims whichfollow. Such variations are to be considered within the scope of theinvention.

What is claimed is:
 1. A method of operating communications system, themethod comprising: operating network device to receive an attach requestmessage corresponding to a UE which received a shared network IDcorresponding to a plurality of service provider networks identified bydifferent network IDs, said first access request message including afirst network identifier of a service provider network which providesservice to said UE, said first network identifier being one of thedifferent network identifiers corresponding to said shared network ID;operating the network device to determine from stored information anetwork address corresponding to said first network ID; and operatingthe access gateway to use: the network address information correspondingto the first network ID and information from the attach request messageto generate a proxied attach request message on behalf of the first UE;and sending the proxied attach request message to the service providercore network corresponding to the first network ID using the determinednetwork address.
 2. The method of claim 1, wherein said network deviceis an access gateway.
 3. A non-transitory computer readable mediumincluding computer executable instructions which when executed by one ormore processors of a communications system cause the communicationssystem to perform the steps of: operating network device to receive anattach request message corresponding to a UE which received a sharednetwork ID corresponding to a plurality of service provider networksidentified by different network IDs, said first access request messageincluding a first network identifier of a service provider network whichprovides service to said UE, said first network identifier being one ofthe different network identifiers corresponding to said shared networkID; operating the network device to determine from stored information anetwork address corresponding to said first network ID; and operatingthe access gateway to use: the network address information correspondingto the first network ID and information from the attach request messageto generate a proxied attach request message on behalf of the first UE;and sending the proxied attach request message to the service providercore network corresponding to the first network ID using the determinednetwork address.